2015-12-28 - 23838 - Spec - Add Trigger for PO Feed Generation #MMPPSupport #mmppreports
SPECIFICATIONS
2015-12-28 - Spec - 23838 Add Trigger for PO Feed
Purpose
Add a trigger point for the PO Feed.
Admin Info
| Purpose |
Add Trigger to PO Feed |
| Requested By |
Baiwa |
| Spec Created By |
Adithya |
| Spec Created Date |
12/29/2015 |
| Spec QA by |
Adithya |
| Objects |
ZSNC_PO_EXTRACT |
| Document Status |
Complete |
Estimates
| Sl.No |
Activity |
Estimation in Hours |
| 1 |
Research |
08 |
| 2 |
Documentation |
08 |
| 3 |
Development/ Config |
32 |
| 4 |
Unit test in DEV |
24 |
| 5 |
Unit test in QUA |
|
| 6 |
Other activity |
|
| TOTAL |
64 |
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]Documents
[Attach any document(s) received for the requirement(s)]
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
| Sl. |
Change Details |
Requested By |
Requested On |
Notes if any |
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]Add a trigger point for PO Feed which is if delivery address is changed in the PO then a PO Feed has to be triggered and the PO Feed file has to be generated.
In Scope:
[List the activities to be included in scope]NB POs for which there is a scope of changing the delivery address
Out of Scope:
[Out of scope activities]Z3NB POs for which the delivery address is grayed out and is not modifiable.
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
Understand that delivery address can only be changed on NB POs and those fields for a Z3NB POs are grayed out and not modifiable.
Program is changed and while testing we have gone through some issues and understood that trigger of PO Feed if there is a change in delivery address fields is complex.
For example: When a New PO is created the delivery address is same as the plant address for NB Pos, if we change the delivery address in the PO line a new address number is created and it is updated in the EKPO table. PO Feed program can identify the change on the PO and it is triggering the PO Feed (extract).
But when we again change the same delivery address of that PO, it is very difficult to identify the change with respect to the PO and trigger the PO Extract and performance can also be changed.
Call on 01/04/2016:
Discussion:
Conveyed that when ever delivery address is updated in the NB PO line item, a new address number is generated which can be seen in the EKPO Table. If we put the generation of new address number as the trigger point, the trigger for the delivery address change is working good for the first time
Before the delivery address is changed/updated, there is no address number in the EKPO table the delivery address is same as the plant address for NB and it is customer address for Z3NB POs.
If there is an update in the delivery address of the PO line:
If we look at the CDHDR the change first delivery address change is triggered with reference to the Purchase Order as shown in the below hence with the logic the first change can be added as the trigger for the PO Feed.
If we change the delivery address again in the same purchase order:
The change in CDHDR is triggered on the address number and not on the purchase order hence adding this change as the trigger may make the program complex in performance.
Discussed with NE on call dated 01/04/2016:
We shall make the program to consider the changes made on ME2* and Object as "ADRESSE" and if there is a latest change in on adress and the corresponding Po has to be triggered.
We also have to make sure the change is triggered only once on the delivery address change. For that we may have to maintain the same logic which is maintained with PO relating to table SNC_PO
01/26/2016: While testing in Street4 & Chinese Character Issue in QAS system, a bug is reported. If the file (PO Feed) is downloaded to local system the file type was UCS-2 Big Indian format, which can be checked in the Note Pad ++, Instead all the shall be UTF-8.
So the changes are commented for PO Feed trigger when the delivery address change so as to send the changes for the encoding Bug on 02/03/2016
Test Plan
[List test scenarios/cases to be executed here]| Test ID |
Test Scenario |
Expected Results |
| PF01 |
Create a PO and execute the PO feed |
PO Feed file has to be generated with all the details in it. |
| PF02 |
Change the shipping Instructions and execute the PO Feed |
Two files are to be generated one for old SI and One for new SI with all the details in both the file and with deletion indicator with old SI |
| PF03 |
Change the Qty, Ex fact date and see all the triggers are working |
Files are to be generated for all the triggers. |
| PF04 |
1. Change the delivery address in the PO line item and execute the PO feed. 2. Change the delivery address again on the same po and execute he PO Feed program 3. Do not do any changes in the delivery address and execute the PO Feed |
1. A PO feed file has to be generated with all the details in it with delivery address same as the changes address 2. A PO Feed file has to be generated with all the details in it with delivery address same as the changes address 3. No File has to be generated. |
Solution Details
[Provide complete technical details for configuration or programming here]
Carry out changes in the program to add delivery address as a trigger for PO Feed
Issues
[List Issues / Bugs identified in configuration or development]